Document management system employing multi-zone parsing process

ABSTRACT

A document management system that converts documents from different sources such as scanners, Fax machines and workstations into electronic documents and provides file management to manage the document storage and retrieval. The system comprises parsing engines that subdivide the document presentation into multiple presentation zones, parse data of each presentation zone with different parsing program or programs to provide output data in format or formats preferable for said zone, and reconstruct the document by recomposing the output presentation of all presentation zones.

BACKGROUND OF THE INVENTION

[0001] 1. Field of the Invention

[0002] The present invention relates to document management system that converts documents from different sources such as scanners, Fax machines and workstations into electronic documents and provides file management facility to manage the storage and retrieval of such documents.

[0003] 2. Background of the Invention

[0004] With the availability of computers and workstations, there was a desire to convert documents into electronic form for efficient editing, storage and management. Since the arrival of the Internet and E-commerce, such desire becomes more apparent. The tasks of converting and managing documents are very complex processes because documents always will be presented and exchanged in both forms: hard copy and electronic forms. To further complicate this matter, electronic documents may be generated from different platforms with different formats and presentation soft wares. A commonly used process is scanning hard-copy documents and storing the images as TIF files before converting to PDF format which provides additional system flexibility. PDF formats can be Image Only PDF formats that encapsulate the TIF files or PDF image and text formats that show both the image and provide access to the OCRed text. In general, all electronic documents produced either by scanning of hard copies or by electronic processes can be converted to PDF formats or any other formats by parsing processes, which place the document presentation data into a print stream and feed it through a parser or parsers. Each parser parses the document data and converts it into the format, which said parser is built for before sending the output data to a repository engine. Typically, PDF format is commonly used for complete document image presentation and XML format is useful for data processing and analysis. However, converting complete documents to a single presentation format inherits several drawbacks such as inflexibility and insufficiency: at minimum, document functionality must include presenting complete and comprehensive image presentation of contained information, providing data for analysis and facilitating avenue for correction or modification. TIF format provides compact storage of image data and viewers for TIF files are available in most workstation, but it is not suitable for data extraction and image modification. PDF is more flexible, it can provide both image and text presentation formats, but modification is difficult and requires additional software. A document may include several presentation zones, each possesses different characteristics, functionalities, and requirements, therefore it is desirable to covert each presentation zone to format that is most suitable for its requirements. The concept of converting different zones of a document into different formats can overcome the shortcomings of converting a complete document into one single format. With the growth of E-commerce across the Internet, users must be able use personal computers to access documents such as application or purchase order forms and modify said forms before submitting. Such documents typically contain static presentation zones including the merchant logo, instructions and general information and dynamic presentation zones where the users fill in other required information. It is advantageous to convert the static zones to image format such as TIF file that is most suitable for viewing only and the dynamic zones to text format such as XML or any other text editor that is best for editing and data extraction, some text editor is available in most personal computers or work station.

SUMMARY OF THE INVENTION AND OBJECTS

[0005] The object of this invention is to provide a document management system that acquires documents from different sources, converts said documents into electronic forms suitable for complete image presentation, data processing and content modification, and contains an efficient file management that is essential for controlling the repository of a massive amount of document data.

[0006] The system of the present invention comprises parsing engines that subdivide the document presentation into multiple presentation zones, parse data of each presentation zone with different parsing program or programs to provide output data in format or formats preferable for said zone, and reconstruct the document by recomposing the output presentation of all presentation zones.

[0007] This and other objects and advantages of this invention will become apparent through examining the following description of the arrangement, operations and functionalities of the constituent components and appended claims in conjunction with the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008]FIG. 1 is a schematic partial illustration of a document management system of the present invention.

[0009] FIG.2 is a schematic partial illustration of a document management service provider system of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0010] The embodiment of the present invention comprises:

[0011] Document acquisition engines 1 that collect document presentation data from document generators 2 such as Fax machines, page scanners and workstations, and convert data to single format data streams 4 such as print streams.

[0012] One or a plurality of parsing engines 3 that parse documents contained in data streams 4 fed into parsing engines 3 from the acquisition engines 1. Parsing engines 3 map each page of input documents into one or a plurality of predetermined presentation zones following the presentation template, parse the presentation of each presentation zone into one or a plurality of output presentation formats determined by the presentation templates, and reconstruct the complete presentation of said page in one or a plurality presentation options by retrieving and placing selected output presentation formats called for by the selected option or options into each presentation zone following the presentation template.

[0013] One or a plurality of repository engines 5 that manage the data storage and retrieval processes of out put data sent from the parsing engines and provide physical storage facilities.

[0014] Referred to FIG. 1, one preferred embodiment of the present invention comprises:

[0015] Document acquisition engines 1 that may include one or a plurality of computers connected to collections of document generators 2 such as Fax machines, page scanners, digital cameras, and workstations. With Fax machines and page scanners, the images are scanned and stored as TIF files by the scan application. TIF files provide compact storage of image data using CCITT Group IV compression. The images from digital cameras are typically collected as JPEG or TIF files. With the workstations, documents can be generated with several software packages such as Solid works, Auto CAD, Pro E and Microsoft word, these documents may be sent to the acquisition engines 1 in the original formats if the acquisition engines support such formats, otherwise they must be converted to TIF or JPEG. The document acquisition engines 1 convert all document data to one single format before sending it to next step in the process. The most readily available format is the print stream, since most software packages include their own device drivers for printing.

[0016] Parsing engines 3 comprising one or a plurality of computers, each may contain mapping programs to map each page of an input document into one or a plurality of predetermined presentation zones following the presentation template, parsing programs to parse the presentation of each presentation zone into one or a plurality of output presentation formats determined by the presentation template, and reconstructing programs to reconstruct the completed presentation of said page in one or a plurality presentation options by retrieving and placing selected output presentation formats called for by the selected option or options into each presentation zone following the presentation template. Each presentation template must be designed specifically for each document type and may include one or a plurality of complete presentation options that have identical presentation zone mapping but different zone presentation formats. Each presentation template comprises complete presentation option identifications, presentation zone identifications, mapped location of each presentation zone, and parsing program identification of each zone for each complete presentation option. Parsing programs may be stored within the parsing engines 3 with unique identifications for retrieval reference. Most parsing programs are commercially available and are selected based on the input and output platforms and formats.

[0017] Repository engines 5 that comprise one or a plurality of computers, each contains data storage hardware such as disk drives, optical drives and tape drives and repository management to manage the data files storage, indexing, searching, and retrieval processes. The repository management may include self-contained file management such as JAR or ZIP and combinations of database such as LDAP, WEBDAV Server, and SOAP Server together with file management such as NIS, NFS, and NTFS.

[0018] It is obvious to a person skilled in the art that, all of the above constituent components and programs can be packed in one computer or can be rearranged in several computers.

[0019] The parsing output presentation format options may include:

[0020] Figure in image presentation format: such as PDF, TIF and JPEG presenting images of figures, drawings, graphs, charts, diagrams, pictures, and text image.

[0021] Text in text format: such as any text editor, ASCII file and XML describing the text content. With this format, the recognition of text symbols is required, and the text can be regenerated with different fonts and sizes.

[0022] Mathematic equation presentation in executable equation format.

[0023] Spreadsheet presentation in executable calculation spreadsheet format such as EXEL spreadsheet.

[0024] Blank presentation format showing blank

[0025] File inserting format for inserting pre-generated file.

[0026] The presentation zone or zones of a document may be categorized into the following categories:

[0027] Static figure in image presentation format zone: wherein the figure images are unchanged with every document of the same type and are presented in image presentation formats such as TIF or JPEG. For examples: company logos, graphic art designs, charts, diagrams, graphs, drawings, pictures, and static text which original image must be preserved.

[0028] Dynamic figure in image presentation format zone: wherein the figure images vary with every document and are presented in image presentation formats such as TIF or JPEC. For examples: personal signature, personal fingerprints, variable charts, graphs, drawings, diagrams, pictures, and dynamic text which original image must be preserved.

[0029] Static text in text format presentation zone: wherein the original text contents must be preserved during the parsing process, and remain unchanged for every document of the same type. Recognition of text symbols is required; the text can be regenerated with different text fonts and sizes, and may be presented in text formats such as XML or any text editor.

[0030] Dynamic text in text format presentation zone: wherein the original text contents must be preserved during the parsing process, but not the original text images, recognition of text symbols is required and the text can be regenerated with different text fonts and sizes. This dynamic text varies with every document, may be edited or modified after parsing, and may be presented in text formats such as XML or any text editor.

[0031] Executable equation format zone: wherein text and standard mathematical symbols such as +, −, ×, /, =, and % form executable equations

[0032] Executable calculation spreadsheet format zone: wherein data is formed into column and rows of spreadsheets that can perform executable calculations.

[0033] No parsing with blank presentation zone: wherein the output presentation is blanked.

[0034] No parsing with file inserting format zone: wherein the output presentation is reconstructed with another data file.

[0035] In general, the parsing process of each document comprises the following steps:

[0036] 1. Retrieve the presentation template for the specific document

[0037] 2. Evoke the mapping program and map the input document into one or a plurality of predetermined presentation zones following the presentation template,

[0038] 3. Select and set the presentation option identification.

[0039] 4. Identify each zone with its presentation zone identification, determine and retrieve the parsing program which identification is assigned to said zone for said option by the presentation template, and parse the presentation of said zone.

[0040] 5. Store parsed data into the document file, which contains the complete presentation data of the said document with references to the presentation option identification and zone identification.

[0041] 6. Repeat steps 4 to 5 until all zones are parsed.

[0042] 7. Repeat steps 3 to 6 until all presentation options are executed.

[0043] The reconstruction process then includes:

[0044] 1. Retrieve the presentation template for the specific document

[0045] 2. Evoke the mapping program and map output presentation into one or a plurality of predetermined presentation zones following the presentation template, identify each zone with its presentation identification.

[0046] 3. Select the presentation option, with the said selected option identification and the zone identifications, retrieve and install parsed data to each zone following the presentation template for the selected option.

[0047] To utilize existing commercially available parsing programs, it is advantageous to employ a multi-layer parsing process wherein the parsing process of a page comprises one or a plurality of parsing layers. In each parsing layer, the mapping program maps the page into parsing zones that to be parsed, following the sub-layer template designed for said sub-layer, and all parsing zones are parsed with the parsing program called for by the sub-layer template. In this process, the presentation template may contain presentation option identifications and all sub-layer templates for each and every presentation option. Each sub-layer template may contain mapped locations of parsing zones to be parsed in said sub-layer, parsing zone identifications and parsing program identification for said sub-layer.

[0048] In general, the multi-layer parsing process of each document comprises the following steps:

[0049] 1. Retrieve the presentation template for the specific document

[0050] 2. Set the presentation option identification, and retrieve all sub-layer templates contained in said option.

[0051] 3. Evoke the mapping program and map the input document into one or a plurality of predetermined presentation zones following each sub-layer template,

[0052] 4. Parse each and every zone in said sub-layer with the parsing program which identification is assigned to said sub-layer until all zones are parsed.

[0053] 5. Store data into the document file, which contains the complete presentation data of the said document with a reference to the presentation option identification, sub-layer identification and zone identification.

[0054] 6. Repeat steps 3 to 5 until each and every sub-layer are parsed

[0055] 7. Repeat steps 2 to 6 until all parsing options are executed.

[0056] The reconstruction process then may includes:

[0057] 1. Retrieve the presentation template for the specific document

[0058] 2. Select the presentation option, and retrieve all sub-layer templates contained in said option.

[0059] 3. Evoke the mapping program and map the output presentation into one or a plurality of predetermined presentation zones following each sub-layer template, and identify the zone identification.

[0060] 4. With the sub-layer identification and zone identification, retrieve and install parsed data into each zone following the said sub-layer template.

[0061] 5. Repeat steps 3 to 4 until each and every sub-layer are reconstructed.

[0062] 6. Reconstruct the complete presentation by superimposing all presentation layers.

[0063] In a parsing process involving several complete presentation options, if a zone is to be parsed with an identical parsing format in more than one complete presentation option, said zone needs to be parsed only once and data may be reused in the reconstruction process.

[0064] To manage the data storage and retrieval processes in the repository engines 5, each document file is characterized by key reference attributes referred as indexing attributes, which may include the organization identification, the document identification, the user identification, the account identification, date of the document, and the document type identification. The document files are placed and organized in the repository engines 5 by using the indexing attributes to determine the storage hierarchy and to construct the indexing logic for searching and retrieval. To automatically identify the document indexing attributes, each parsing engine further comprises a program to map out the document indexing attribute zones following the indexing template, the presentation of each document indexing attribute zone is parsed into text in text format and is stored as the document indexing attribute data in the indexing file.

[0065] In many applications wherein the complete presentation of documents is not required or needs to be stored strictly for archival purpose, only some key data is accessed frequently for data processing and analysis. It is advantageous to parse the said key data separately and store it as resume data in the resume file, which is often organized into spreadsheet format in the output presentation. It is conceivable to extract the indexing attribute data and the resume data from the complete presentation parsing process if the zones containing such data are parsed with text format options.

[0066] For efficiency, the repository engines may contain three directories: the indexing directory that stores the indexing files, the resume directory that stores the resume files and the document directory that stores the document files. The storage hierarchy of the indexing directory is organization identification, user identification and the file name is the document identification, wherein the storage hierarchy of the resume and document directories is organization identification and the file name is the document identification.

[0067] The document file searching and retrieval process then comprises these following steps:

[0068] 1 Enter the indexing directory.

[0069] 2 Using two indexing attributes: the organization identification and the user identification, search and open the indexing data of all documents belong to the said user.

[0070] 3 From the indexing data of indexing files, using other indexing attributes such as document type identification, account identification and date to determine the specific file that is searched for, and identify the document identification for the next step.

[0071] 4 Enter the resume and document directories.

[0072] 5 Search and retrieve the resume and document files using two indexing attributes: the organization identification and the document identification.

[0073] The file searching process can be automated with a file management program such as JAR file and ZIP file, and the procedure comprises the following steps:

[0074] 1 The user enters the organization identification and the user identification.

[0075] 2 The repository engine 5 evokes the searching program in the file management program.

[0076] 3 The searching program enters the indexing directory, retrieves the indexing attributes data of all documents belong to said user in said organization, constructs, and displays an indexing table, which contains all indexing attributes of all document in an organized fashion following a predetermined grouping hierarchy.

[0077] 4 The user selects the document using other indexing attributes.

[0078] 5 The searching program enters the resume and document directories and uses the organization identification and document identification to locate and retrieve the resume and document files of the document selected by the user.

[0079] The presentation templates, indexing templates and the resume templates may be stored in the repository engines 5 or be included in the data stream sent to the repository engines, For performance however, the parsing engines 3 may contain all templates of documents to be parsed by said parsing engines. The indexing template is identical for all documents. The presentation templates and the resume templates vary with the organizations and the document types, they are stored with two indexing attributes: the organization identification and the document type identification.

[0080] The parsing process comprises:

[0081] Load the indexing template.

[0082] Parse the document indexing attribute zones to identify the organization identification the document type identification and all other indexing attributes, and store data in the indexing file.

[0083] With the organization identification and the document type identification, retrieve and load the resume template.

[0084] Parse the resume zones, collect and store the resume data.

[0085] With the organization identification and the document type identification, retrieve and load the presentation template.

[0086] Parse the presentation zones, collect and store the presentation data.

[0087] The image reconstruction process comprises:

[0088] With the organization identification and the document type identification, retrieve and load the presentation template.

[0089] With the document identification, retrieve the presentation data and reconstruct the document image following the presentation template.

[0090] To further improve the parsing efficiency for all documents of the same type, the static figures and the static text in image presentation format are generated in advance by either parsing process or electronic composition, and stored in the parsing engines 3 with two indexing attributes: organization identification and document type identification, the zones containing said static figures and text are designated as No parsing with file inserting format in the presentation templates. During the reconstructing process, the pre-generated image data of the static figures and text are retrieved and inserted back into the said zones following the presentation templates. This approach not only minimizes the required storage space, it also reduces the parsing time, reconstructing time and the data transmitting time.

[0091] With the expansion of E-commerce across the Internet, many businesses not only need to provide static information promoting their images, products and services, they must also interact with customers or clients. Interaction by exchanging documents such as purchase orders, service request applications, billing statements, shipment status, and transaction statements, requires complex document management and expensive development effort. Therefore, it is desirable to contract out this type of file management to a service provider, especially for small organizations that have limited resources and capital. In general, a document service provider system as illustrated in FIG, 2 comprises:

[0092] A host document management system 11 that is locally located at the facility of said service provider. The said host document management system comprises one or a plurality of Web server engines 12 that facilitate the communication services such as receiving and responding to the user requests between the host document management system 11 and a collection of Internet user systems 13, security engines 14 such as LDAP servers for authenticating users and authorizing services, host parsing engines 19 for parsing documents, host repository engines 20 for storing output data and host communication engines 16 for controlling the communication between the host and the client systems. The Web server engines 12 may include one or a plurality of Web page templates for each organization and Web page re-composition programs, which compose the Web pages by filling in the templates with related data retrieved from the host repository engines 20. The Web page templates are preferably generated in HTML conforming to XML format and the Web page re-composition program is preferably written in JAVA class. The re-composition program may be designed to further include means for modifying the Web page templates dynamically by the system administrators.

[0093] One or a plurality of client document management systems 17 that is remotely located at the facilities of the service subscribers and is linked to the host system 11 across the Internet. Each of the said client document management systems 17 comprises client parsing engines 21 for parsing documents, client repository engines 22 for storing output data from the parsing engines 21, client communication engines 23 for controlling the communication between the host system 11 and the said client system and document acquisition engines 24 to collect document presentation data from a collection of client document generators 25 and computers 18; the document acquisition engines 24 convert data into one single format, envelop all data into data streams and send said data streams to the client parsing engines 21. The parsed data is sent across the Internet to the host document management system 11 where the documents are reconstructed by the host parsing engines 19. Data is stored at either the client repository engines 22 or the host repository engines 20 or both. This type of set up is more suitable for subscribers who have large workload requirements. To improve efficiency by reducing data storage space and cutting down the time required for parsing, reconstructing, and data transmitting, the static figures and text in image presentation format of documents of the same types are generated in advance and stored in the host parsing engines 19 that service the said types of document. The stored static data is later used for the document reconstruction process. Since only the dynamic data is sent across the Internet, it automatically provides additional security measure due to the fact that the intruders have no templates and static data to reconstruct the complete documents.

[0094] One or a plurality of client document acquisition engines 26 that are remotely located at the facilities of the service subscribers. The document acquisition engines 26 collect document presentation data from a collection of client document generators 27 and computers 28, convert data into one single format, envelop all data into data streams and send said data streams across the Internet to the host system 11 where the documents are parsed, and reconstructed by the host parsing engines 19. Data is stored at the host repository engines 20. This type of set up is more suitable for subscribers who have small workload requirements.

[0095] Communication across the Internet is an effective way to reduce the communication infrastructure cost, however, it puts the data security at risk. Virtual Private Network (VPN) may be implemented to provide secure connections across the Internet between the host system and the client systems. The VPN encapsulates the IP data gram in order to maintain data privacy and integrity. To improve the level of security protection, the communication engines may further include firewalls and other security measures.

[0096] As parts of two ways communication, the authorized users may request for documents and fill in required information or make modifications before sending said documents back directly to the service subscribers who are responsible for processing and responding to the said documents. It is possible that the modified documents are sent to and stored at the service provider system 11 for later retrieval by the service subscribers. The service subscribers may elect to post the status and results of their responses through the document management service provider where the users may gain access, view, and keep track of the responses. 

Having described and disclosed my invention, I claim:
 1. A document management system that comprises: One or a plurality of parsing engines that parse documents contained in data streams fed into said parsing engines. Each one of the parsing engines may contain mapping programs to map each page of an input document into one or a plurality of predetermined presentation zones following the presentation template, parsing programs to parse the presentation of each presentation zone into one or a plurality of output presentation formats determined by the presentation template, and reconstructing programs to reconstruct the completed presentation of said page in one or a plurality presentation options by retrieving and placing selected output presentation formats called for by the specific presentation option or options into each presentation zone following the presentation template. One or a plurality of repository engines to store the output data sent from the parsing engines.
 2. A document management system of claim 1 wherein a parsing engine may retrieve the output data of a document parsed by another parsing engine and reconstruct said document.
 3. A document management system of claim 2 wherein the parsing process of a page comprises one or a plurality of parsing layers. In each parsing layer, the mapping program maps the page into parsing zones to be parsed, following the sub-layer template designed for said sub-layer, and all parsing zones are parsed with the parsing program called for by the sub-layer template.
 4. A document management system of claim 3 wherein the reconstruction process of the complete presentation of a page may include the superimposing of all reconstructed sub-layer presentations.
 5. A document management system of claim 2 wherein the output presentation format options comprise: Figure in image presentation format. Text in text format describing the text content. In this format, the recognition of text symbols is required, and the text can be regenerated with different fonts and sizes. Mathematic equation presentation in executable equation format. Spreadsheet presentation in executable calculation spreadsheet format. Blank presentation format showing blank File inserting format for inserting pre-generated file.
 6. A document management system of claim 5 wherein the presentation zone categories may include: Static figure in image presentation format zone wherein the figure images are unchanged with every document of the same type and are presented in image presentation formats. Dynamic figure in image presentation format zone wherein the figure images may vary with every document and are presented in image presentation formats. Static text in text format presentation zone wherein the original text contents remain unchanged for every document of the same type and must be preserved during the parsing process. The text is presented in text format and can be regenerated with different text fonts and sizes. Dynamic text in text format presentation zone wherein the original text contents may vary with every document and must be preserved during the parsing process. The text is presented in text format and can be regenerated with different text fonts and sizes. Executable equation format zone wherein text and standard mathematical symbols such as +, −, ×, / and % form executable equations. Executable calculation spreadsheet format zone wherein data is formed into columns and rows of spreadsheets that can perform executable calculations. No parsing with blank presentation zone wherein the output presentation is blanked. No parsing with file inserting format zone wherein the output presentation is reconstructed with pre-generated data files.
 7. A document management system of claim 6 wherein the parsing process further comprises document resume parsing process, which parses the resume zones containing the document key descriptive attributes into text format presentation following the resume template. The output data is stored as resume file.
 8. A document management system of claim 7 wherein the parsing process further comprises document indexing parsing process, which parses the indexing attribute zones containing the document key indexing attributes into text format presentation following the indexing template. The output data is stored as indexing file.
 9. A document management system of claim 8 wherein the document indexing attributes may include the organization identification, the document identification, the user identification, the account identification, and the document type identification.
 10. A document management system of claim 9 wherein the parsing engines may contain the presentation templates, the resume templates and the indexing template of documents to be parsed by said parsing engine. The indexing template is identical for all documents. The presentation templates and the resume templates vary with the organizations and the document types, and may be stored with two indexing attributes: the organization identification and the document type identification.
 11. A document management system of claim 10 wherein the parsing process comprises: Load the indexing template. Parse the document indexing attribute zones to identify the organization identification and the document type identification. Load the resume template. Parse the resume zones, collect, and store the resume data. Load the presentation template. Parse the presentation zones, collect, and store the presentation data.
 12. A document management system of claim 11 wherein the image reconstruction process comprises: Load the presentation template. Retrieve the presentation data and reconstruct the document image following the presentation template.
 13. The document management system of claim 8 wherein the repository engine may contain three directories: the indexing directory that stores the indexing files, the resume directory that stores the resume files and the document directory that stores the document files containing the output document presentation data.
 14. The document management system of claim 13 wherein the storage hierarchy of the indexing directory is the organization identification, the user identification, and the file name is the document identification.
 15. The document management system of claim 13 wherein the storage hierarchy of the resume and document directories is the organization identification, and the file name is the document identification.
 16. The document management system of claim 14 wherein the storage hierarchy of the resume and document directories is the organization identification, and the file name is the document identification.
 17. The document management system of claim 16 wherein the document file searching process comprises: Enter the indexing directory Using two indexing attributes: the organization identification and the user identification, search and open the indexing data of all documents belong to the said user. From the indexing data of indexing files, using other indexing attributes such as document type identification, account identification and date to determine the specific file that is searched for, and identify the document identification for the next step. Enter the resume and document directories. Search and retrieve the resume and document files using two indexing attributes: the organization identification and the document identification.
 18. The document management system of claim 16 wherein the document file searching process comprises: The user inputs the organization identification and the user identification. The repository engine enters the indexing directory, retrieves the indexing attributes data of all documents belong to said user in said organization, constructs, and displays an indexing table, which contains all indexing attributes of all document in an organized fashion following a predetermined grouping hierarchy. The user selects the document using other indexing attributes. The repository engine enters the resume and document directories and uses the organization identification and document identification to locate and retrieve the resume and document files of the document selected by the user.
 19. A document management system of claim 9 wherein the static figures and text in image presentation format are generated in advance and stored in the parsing engines with two indexing attributes: organization identification and document type identification and the zones containing said static figures and text are designated as No parsing with file inserting format by the presentation templates. During the reconstruction process, the static figures and text are retrieved and inserted back into said zones following the presentation templates.
 20. A document management system of claim 6 wherein the zones containing the document key descriptive attributes are parsed into text format presentation.
 21. A document management system of claim 6 wherein the zones containing the document key indexing attributes are parsed into text format presentation.
 22. A document management system of claim 21 wherein the zones containing the document key descriptive attributes are parsed into text format presentation.
 23. A document management system of claim 1 which further comprises one or a plurality of document acquisition engines that collect document presentation data from document generators, convert data into one single format, envelop data into data streams and send said data streams to the parsing engines.
 24. A document management service provider comprising: A host document management system that is locally located at the facility of said service provider. The said host document management system comprises one or a plurality of Web server engines that facilitate the communication services such as receiving and responding to the user requests between the host document management system and a collection of Internet user systems, security engines for authenticating users and authorizing services, host parsing engines for parsing documents, host repository engines for storing output data and host communication engines for controlling the communication between the host and the client systems. One or a plurality of client document management systems that is remotely located at the facilities of the service subscribers and is linked to the host system across the Internet. Each of the said client document management systems comprises client parsing engines for parsing documents, client repository engines for storing output data from the client parsing engines, client communication engines for controlling the communication between the host system and the said client system and document acquisition engines to collect document presentation data from a collection of client document generators and computers; the document acquisition engines convert data into one single format, envelop data into data streams and send said data streams to the client parsing engines. The parsed data is sent across the Internet to the host document management system where the documents are reconstructed by the host parsing engines. Data is stored at either the client repository engines or the host repository engines or both. One or a plurality of client document acquisition engines those are remotely located at the facilities of the service subscribers. The document acquisition engines collect document presentation data from a collection of client document generators and computers, convert data into one single format, envelop data into data streams and send said data streams across the Internet to the host system where the documents are parsed, and reconstructed by the host parsing engines. Data is stored at the host repository engines. 